Services Utility: Windows Management Instrumentation Service
| Display Name (?): | Windows Management Instrumentation | ||||||||||||||
| Short Name (?): | winmgmt | ||||||||||||||
| Executable (?): | svchost.exe | ||||||||||||||
| Library (?): | WMIsvc.dll | ||||||||||||||
| Depends On (?): | Remote Procedure Call (RPC) | ||||||||||||||
| Supports (?): | IPv6 Helper Service, Security Center, Windows Firewall/Internet Connection Sharing (ICS) | ||||||||||||||
| Description (?): | Provides a common interface and object model to access management information about operating system, devices, applications and services. If this service is stopped, most Windows-based software will not function properly. If this service is disabled, any services that explicitly depend on it will fail to start. | ||||||||||||||
| OS (?): | XP Home/Professional, Vista Home/Business, NT4 Server, 2000 Server, Server 2003, Vista Server | ||||||||||||||
| Startup (?): |
| ||||||||||||||
Explanation (?): | The Windows Management Instrumentation service provides the mechanism for the Microsoft implementation of Web-based enterprise management (WBEM) that uses the common information model (CIM) to represent managed components. This service is meant to be accessed through programming and scripting languages to access Windows subsystems, which can do everything from list services to restart the computer to install drivers, etc. It is very complex and very advanced, but it is considered a required service. This service should be let to automatic, and if set to manual or disabled then Windows programs or services may misbehave. In the very least WMI enumeration cannot occur without this service. In my experience I have found that Windows operates without it, but there could be many side effects that I have not tested for. |